<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Avisi Blog</title>
	<atom:link href="https://blog.avisi.nl/feed/" rel="self" type="application/rss+xml" />
	<link>https://blog.avisi.nl</link>
	<description>Software Craftsmanship through Java, Atlassian &#38; IT Quality</description>
	<lastBuildDate>Wed, 29 Mar 2017 09:05:49 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>Integration best practices &#8211; Service robustness</title>
		<link>https://blog.avisi.nl/2017/03/27/integration-best-practices-service-robustness/</link>
		<comments>https://blog.avisi.nl/2017/03/27/integration-best-practices-service-robustness/#comments</comments>
		<pubDate>Mon, 27 Mar 2017 08:12:20 +0000</pubDate>
		<dc:creator>Geert Liet</dc:creator>
				<category><![CDATA[Integration]]></category>
		<category><![CDATA[Technical]]></category>
		<category><![CDATA[integration]]></category>
		<category><![CDATA[microservices]]></category>
		<category><![CDATA[soa]]></category>

		<guid isPermaLink="false">https://blog.avisi.nl/?p=6497</guid>
		<description><![CDATA[My previous blog post on integration best practices gave some general thoughts on service development. When designing services one of the most important parts is resilience of your services and make sure that failure of one services doesn&#8217;t collapse your &#8230; <a href="https://blog.avisi.nl/2017/03/27/integration-best-practices-service-robustness/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>https://blog.avisi.nl/2017/03/27/integration-best-practices-service-robustness/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>3 major differences between a traditional Atlassian add-on and a cloud add-on</title>
		<link>https://blog.avisi.nl/2017/03/01/3-major-differences-between-a-traditional-atlassian-add-on-and-a-cloud-add-on/</link>
		<comments>https://blog.avisi.nl/2017/03/01/3-major-differences-between-a-traditional-atlassian-add-on-and-a-cloud-add-on/#comments</comments>
		<pubDate>Wed, 01 Mar 2017 07:33:51 +0000</pubDate>
		<dc:creator>Gert-Jan van de Streek</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">https://blog.avisi.nl/?p=6488</guid>
		<description><![CDATA[We are in Amsterdam for Atlassian connect week. The goal for us this week is to port an existing add-on to the Atlassian cloud. It is still JIRA and Confluence in the cloud, but traditional add-ons can&#8217;t be installed. So what &#8230; <a href="https://blog.avisi.nl/2017/03/01/3-major-differences-between-a-traditional-atlassian-add-on-and-a-cloud-add-on/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>https://blog.avisi.nl/2017/03/01/3-major-differences-between-a-traditional-atlassian-add-on-and-a-cloud-add-on/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Visiting Atlassian Connect Week in Amsterdam</title>
		<link>https://blog.avisi.nl/2017/02/28/visiting-atlassian-connect-week/</link>
		<comments>https://blog.avisi.nl/2017/02/28/visiting-atlassian-connect-week/#comments</comments>
		<pubDate>Tue, 28 Feb 2017 07:28:08 +0000</pubDate>
		<dc:creator>Gert-Jan van de Streek</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">https://blog.avisi.nl/?p=6481</guid>
		<description><![CDATA[Atlassian Connect week is in full swing and we are there with a team! We are meeting people from all over the world, from Portugal to Mexico and Australia. Curious about what we are doing and why we are there?Atlassian &#8230; <a href="https://blog.avisi.nl/2017/02/28/visiting-atlassian-connect-week/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>https://blog.avisi.nl/2017/02/28/visiting-atlassian-connect-week/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Boiler room testing</title>
		<link>https://blog.avisi.nl/2017/02/14/boiler-room-testing/</link>
		<comments>https://blog.avisi.nl/2017/02/14/boiler-room-testing/#comments</comments>
		<pubDate>Tue, 14 Feb 2017 17:40:20 +0000</pubDate>
		<dc:creator>Gert-Jan van de Streek</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">https://blog.avisi.nl/?p=6470</guid>
		<description><![CDATA[My team is using Kanban. A key tenet of kanban is to limit the amount of work in progress (WIP). Work-in-progress limits highlight bottlenecks in the team&#8217;s process due to lack of focus, people, or skill sets. For us this is &#8230; <a href="https://blog.avisi.nl/2017/02/14/boiler-room-testing/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>https://blog.avisi.nl/2017/02/14/boiler-room-testing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why I switched to Emacs, but never left vi</title>
		<link>https://blog.avisi.nl/2017/01/30/why-i-switched-to-emacs-but-never-left-vi/</link>
		<comments>https://blog.avisi.nl/2017/01/30/why-i-switched-to-emacs-but-never-left-vi/#comments</comments>
		<pubDate>Mon, 30 Jan 2017 15:02:27 +0000</pubDate>
		<dc:creator>Gert-Jan van de Streek</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">https://blog.avisi.nl/?p=6459</guid>
		<description><![CDATA[Because I feel there is a shortage on blogs, long opiniated comparisons and hateful flamewars on Emacs versus vi, I thought I&#8217;d write something about it myself. I am kidding of course (just in case you missed that joke). Some &#8230; <a href="https://blog.avisi.nl/2017/01/30/why-i-switched-to-emacs-but-never-left-vi/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>https://blog.avisi.nl/2017/01/30/why-i-switched-to-emacs-but-never-left-vi/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How code reviews work</title>
		<link>https://blog.avisi.nl/2017/01/25/how-code-reviews-work/</link>
		<comments>https://blog.avisi.nl/2017/01/25/how-code-reviews-work/#comments</comments>
		<pubDate>Wed, 25 Jan 2017 22:42:54 +0000</pubDate>
		<dc:creator>Gert-Jan van de Streek</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">https://blog.avisi.nl/?p=6450</guid>
		<description><![CDATA[Since all the reall fuss started about pairing and code reviews I&#8217;ve only seen one approach in code reviews work really well and that&#8217;s pull requests. Pull requests force a peer review and if you implement them well, they rarely &#8230; <a href="https://blog.avisi.nl/2017/01/25/how-code-reviews-work/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>https://blog.avisi.nl/2017/01/25/how-code-reviews-work/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How we got CISSP&#8217;s</title>
		<link>https://blog.avisi.nl/2017/01/18/how-we-got-cissps/</link>
		<comments>https://blog.avisi.nl/2017/01/18/how-we-got-cissps/#comments</comments>
		<pubDate>Wed, 18 Jan 2017 13:58:58 +0000</pubDate>
		<dc:creator>Daisy Rasing-de Joode</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">https://blog.avisi.nl/?p=6445</guid>
		<description><![CDATA[Barri Jansen and I went back into the school banks last year. Mid-2016 we decided to affirm our security related knowledge by getting the CISSP-title. CISSP stands for Certified Information System Security Professional (Lord, how I hate those unpronounceable titles) and is the &#8230; <a href="https://blog.avisi.nl/2017/01/18/how-we-got-cissps/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>https://blog.avisi.nl/2017/01/18/how-we-got-cissps/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Scaling Business Agility in the Enterprise with SAFe, JIRA Portfolio and JIRA Software</title>
		<link>https://blog.avisi.nl/2016/10/12/scaling-business-agility-in-the-enterprise-with-safe-jira-portfolio-and-jira-software/</link>
		<comments>https://blog.avisi.nl/2016/10/12/scaling-business-agility-in-the-enterprise-with-safe-jira-portfolio-and-jira-software/#comments</comments>
		<pubDate>Wed, 12 Oct 2016 04:03:29 +0000</pubDate>
		<dc:creator>Jaap Weber</dc:creator>
				<category><![CDATA[Agile]]></category>
		<category><![CDATA[Atlassian Partnership]]></category>

		<guid isPermaLink="false">https://blog.avisi.nl/?p=6421</guid>
		<description><![CDATA[It has been almost 3 years since Sander Brienen wrote the post &#8220;Scaling Agile in the Enterprise with SAFe and JIRA Agile &#8221; and had his talk at Atlassian Summit 2013. Sander&#8217;s premise to view an organisation in three levels &#8230; <a href="https://blog.avisi.nl/2016/10/12/scaling-business-agility-in-the-enterprise-with-safe-jira-portfolio-and-jira-software/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>https://blog.avisi.nl/2016/10/12/scaling-business-agility-in-the-enterprise-with-safe-jira-portfolio-and-jira-software/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Making computer games is no game &#8211; customer feedback is king</title>
		<link>https://blog.avisi.nl/2016/09/06/making-computer-games-is-no-game-customer-feedback-is-king/</link>
		<comments>https://blog.avisi.nl/2016/09/06/making-computer-games-is-no-game-customer-feedback-is-king/#comments</comments>
		<pubDate>Tue, 06 Sep 2016 13:24:56 +0000</pubDate>
		<dc:creator>Jaap Weber</dc:creator>
				<category><![CDATA[Agile]]></category>

		<guid isPermaLink="false">https://blog.avisi.nl/?p=6412</guid>
		<description><![CDATA[I have a not so guilty pleasure. It&#8217;s playing computer games. At the moment, my go to game is Tom Clancy&#8217;s The Division from Massive Entertainment. The game is beautifully made and really immersive. I really get the feeling I &#8230; <a href="https://blog.avisi.nl/2016/09/06/making-computer-games-is-no-game-customer-feedback-is-king/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>https://blog.avisi.nl/2016/09/06/making-computer-games-is-no-game-customer-feedback-is-king/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Our agile journey towards a fancy ISMS &#8211; Part 4</title>
		<link>https://blog.avisi.nl/2016/08/03/our-agile-journey-towards-a-fancy-isms-part-4/</link>
		<comments>https://blog.avisi.nl/2016/08/03/our-agile-journey-towards-a-fancy-isms-part-4/#comments</comments>
		<pubDate>Wed, 03 Aug 2016 15:24:15 +0000</pubDate>
		<dc:creator>Daisy Rasing-de Joode</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">https://blog.avisi.nl/?p=6407</guid>
		<description><![CDATA[We, Avisi, have started an agile journey. A journey with one destination: a fancy ISMS for Avisi. I gladly take you along on our trip, by blogging about the adventures we’ve been through. So fasten your seatbelt, we will travel &#8230; <a href="https://blog.avisi.nl/2016/08/03/our-agile-journey-towards-a-fancy-isms-part-4/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>https://blog.avisi.nl/2016/08/03/our-agile-journey-towards-a-fancy-isms-part-4/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
